monorepo: migrate to pnpm#4139
Closed
gabrocheleau wants to merge 78 commits intomasterfrom
Closed
Conversation
…ethereumjs-monorepo into feat/migrate-to-pnpm
29b624a to
1a7faf3
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Contributor
Author
|
Closing this as it this will require a fair amount of additional work (notably to handle CI), is super breaking + we've seemed to mitigate the cross-OS issues with npm |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR migrates npm to pnpm, notably to address issues where npm packagel-lock is generate to be environment specific (e.g. Linux or Mac). Pnpm allows cross-platform lockfiles.